Managing Device Connections
When the connections between the OVOC server and the managed devices traverse a NAT or firewall, direct connections cannot be established (both for OVOC > Device connections and for Device > OVOC connections). OVOC provides methods for overcoming this issue. These methods can be used for both initial setup and Second-Day management:
| ■ | Establishing OVOC-Devices Connections |
| ■ | Establishing Devices - OVOC Connections |
The table below describes the different connection scenarios.
Device Connection Scenarios
|
Configuration Option/Deployment Scenario |
OVOC |
Devices |
||||||
|---|---|---|---|---|---|---|---|---|
|
AWS |
Azure |
On-Premises |
Public Network |
AWS |
Azure |
On-Premises |
||
|
AudioCodes SBC Devices |
||||||||
| Cloud Architecture Mode | Ö |
Ö |
|
- |
Ö |
Ö |
Ö |
|
| OVOC Server Configured with Public IP | Ö |
Ö |
Ö |
Ö |
Ö |
Ö |
Ö |
|
For OVOC Managed devices: All remote connections for OVOC managed devices require a configured WAN interface on the managed device.